h: Let's go for something like the following here:

const exceptionIsObject = typeof exception === 'object' && exception !== null;
const exceptionStatusCode = exceptionIsObject && 'status' in exception ? exception.status : null;
const exceptionErrorProperty = exceptionIsObject && 'error' in exception ? exception.error : null;

// Only report expected errors
// - ExpectedNestJS control flow errors that with status codes like NestJS' `HttpException` errors will have a `status` property.
// - NestJS' expected `RpcExceptions` will have an `error` property
if (exceptionStatusCode === null && exceptionErrorProperty === null) {
    captureException(exception, {
        mechanism: {
        handled: false,
        },
    });
}

return originalCatch.apply(target, [exception, host]);

Why? It's not immediately obvious to me how that improves the current implementation

The current implementation will throw if the error is nullish, which can always happen. We should avoid doing any type casts (as) as much as possible. The change I suggested does runtime checks not to throw when nullish values are passed.

Also, we should add documentation. Somebody who comes across the code is basically in the dark what it means to look on the status or error props.

Ok sure, thanks for clarifying. Will update

l: I would flip the condition: We report the error if this and this condition is true. To me the early return is a weird pattern here but I'll leave it up to you.

This breaks NestJS projects which don't use @nestjs/microservices.

I've tried creating an issue, but couldn't submit it because GH kept showing "Something went wrong" popup.

Thanks for writing in! I am currently working on a fix for the nest SDK and will remove the dependency again as part of that PR. ref